209-chiedge-depending-on-label-block-traffic-to-local-networks #244
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this globalnetwork policy can be used to prevent egress from a host to private IPs. This policy targets hostendpoints, which in turn define which host interfaces are affected. As it affects flows passing through said host interfaces, it acts to restrict policy that targets workloads, rather than interfaces. Example: Namespaced networkpolicy permits egress traffic from container1 to container2 within the same namespace. As the destination is a known endpoint to calico, it is included in "selector: all()" in the allow block of this policy, and the Deny rule is not applied, despite traffic going to a private IP. However, traffic from said container1 OR from services on the host itself to a private IP not present in kubernetes, will be blocked by the second rule. WARNING: It's not clear what will happen in the case where a kubernetes endpoint exists that overlaps with a local IP address.
msherman64
force-pushed
the
209-chiedge-depending-on-label-block-traffic-to-local-networks
branch
from
c788d50 to
cdfb5e9
Compare
msherman64
deleted the
209-chiedge-depending-on-label-block-traffic-to-local-networks
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this globalnetwork policy can be used to prevent egress from a
host to private IPs. This policy targets hostendpoints, which in turn
define which host interfaces are affected.
As it affects flows passing through said host interfaces, it acts to
restrict policy that targets workloads, rather than interfaces.
Example:
Namespaced networkpolicy permits egress traffic from container1 to container2
within the same namespace. As the destination is a known endpoint to calico,
it is included in "selector: all()" in the allow block of this policy, and the
Deny rule is not applied, despite traffic going to a private IP.
However, traffic from said container1 OR from services on the host itself to a
private IP not present in kubernetes, will be blocked by the second rule.
WARNING:
It's not clear what will happen in the case where a kubernetes endpoint exists that
overlaps with a local IP address.